Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e545b42244e1adf219f4fc0e6e9c934487e8416719fe84247a73f8bc46c4126a

Tx prefix hash: 8c947a5fcd9c9e6aa1e66239699f58be1b90adec9c6a28a6ff94d1e2b7ce88ac
Tx public key: 17899217cb77f0c76384cf2fcaee8d1645e5853f49d3bd287b9c970437ea470a
Timestamp: 1630044339 Timestamp [UCT]: 2021-08-27 06:05:39 Age [y:d:h:m:s]: 03:096:00:33:42
Block: 321653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 843150 RingCT/type: yes/0
Extra: 0117899217cb77f0c76384cf2fcaee8d1645e5853f49d3bd287b9c970437ea470a02110000003206faf294000000000000000000

1 output(s) for total of 52.750981573000 dcy

stealth address amount amount idx
00: 154455e3b4d0f18b0e41c0581b552d2ccc815ee098e305902608b073adb7ac92 52.750981573000 667658 of 0

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": 321663, "vin": [ { "gen": { "height": 321653 } } ], "vout": [ { "amount": 52750981573, "target": { "key": "154455e3b4d0f18b0e41c0581b552d2ccc815ee098e305902608b073adb7ac92" } } ], "extra": [ 1, 23, 137, 146, 23, 203, 119, 240, 199, 99, 132, 207, 47, 202, 238, 141, 22, 69, 229, 133, 63, 73, 211, 189, 40, 123, 156, 151, 4, 55, 234, 71, 10, 2, 17, 0, 0, 0, 50, 6, 250, 242, 148, 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