Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aa5096a930c2fc785939ce25d88a47d7096c866e9a4d9003fd451c9ebffebb4

Tx prefix hash: 036e78a64804b7c0d4d7d6046df1baa5788d4d6a6d17c3c13509a9b8ad3b2d5a
Tx public key: a0583646049fb4a3258008c16ed149b0116282dd39a5308eeea42f4198279eaa
Timestamp: 1734094590 Timestamp [UCT]: 2024-12-13 12:56:30 Age [y:d:h:m:s]: 00:102:10:21:19
Block: 1174320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72968 RingCT/type: yes/0
Extra: 01a0583646049fb4a3258008c16ed149b0116282dd39a5308eeea42f4198279eaa021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a142d1757f363935d1e360658c72eee999a6af05a7dc04f23320f7dabc6438c2 0.600000000000 1660457 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": 1174330, "vin": [ { "gen": { "height": 1174320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a142d1757f363935d1e360658c72eee999a6af05a7dc04f23320f7dabc6438c2" } } ], "extra": [ 1, 160, 88, 54, 70, 4, 159, 180, 163, 37, 128, 8, 193, 110, 209, 73, 176, 17, 98, 130, 221, 57, 165, 48, 142, 238, 164, 47, 65, 152, 39, 158, 170, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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