Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b77f653e6933c94125d2de0197e429491f3dbb2e7edd0c77dabf7fe7868a385e

Tx prefix hash: 3a570c484a2a0596a46d1154f5091dac348a47ff1a6194d9effa369b381ee4c4
Tx public key: 2352fff9e58f4a9c86bd48c211f82d4616ab11e6249f7ab2721f7aaa93cb3883
Timestamp: 1723747011 Timestamp [UCT]: 2024-08-15 18:36:51 Age [y:d:h:m:s]: 01:085:21:19:09
Block: 1088617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319849 RingCT/type: yes/0
Extra: 012352fff9e58f4a9c86bd48c211f82d4616ab11e6249f7ab2721f7aaa93cb3883021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61ead56b49b782be5d2c721b11cd71a6a9566e040d0c0b4a956ebc277206199e 0.600000000000 1563234 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1088627, "vin": [ { "gen": { "height": 1088617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61ead56b49b782be5d2c721b11cd71a6a9566e040d0c0b4a956ebc277206199e" } } ], "extra": [ 1, 35, 82, 255, 249, 229, 143, 74, 156, 134, 189, 72, 194, 17, 248, 45, 70, 22, 171, 17, 230, 36, 159, 122, 178, 114, 31, 122, 170, 147, 203, 56, 131, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8