Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e2f3359433df45257f5bcc8dc29759d2d6ce3309ded4fab8b922cbe1dcfd82

Tx prefix hash: 95ded39bb68275fe1c29edffa5deea597fa3c37af38c5829081cb76a389f7333
Tx public key: 4499dd8c100c0cb40a14d3c6ce1ed1cf30b9d0c9253889988f48cdb2f38d9b3f
Timestamp: 1695928386 Timestamp [UCT]: 2023-09-28 19:13:06 Age [y:d:h:m:s]: 01:227:00:16:14
Block: 858199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423315 RingCT/type: yes/0
Extra: 014499dd8c100c0cb40a14d3c6ce1ed1cf30b9d0c9253889988f48cdb2f38d9b3f02110000000a4b8f5122000000000000000000

1 output(s) for total of 0.879894296000 dcy

stealth address amount amount idx
00: 1083b7e6d6a26868f8dc2c02f927de4dfd0971a2d4dbf8961d89e5a1059f2814 0.879894296000 1312365 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": 858209, "vin": [ { "gen": { "height": 858199 } } ], "vout": [ { "amount": 879894296, "target": { "key": "1083b7e6d6a26868f8dc2c02f927de4dfd0971a2d4dbf8961d89e5a1059f2814" } } ], "extra": [ 1, 68, 153, 221, 140, 16, 12, 12, 180, 10, 20, 211, 198, 206, 30, 209, 207, 48, 185, 208, 201, 37, 56, 137, 152, 143, 72, 205, 178, 243, 141, 155, 63, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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