Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df72623a79dcfb42a9c758b217645406c94bec005b2cc15c436835eb6ed035d3

Tx prefix hash: fc23ed44e41519dc0f82a9980662b7a29b922fbac83b137acbe4e5e45dc5d898
Tx public key: 20f1c7995c6440e550e0e92650d517a9d53b7af21bfa5e37d9e28e5eb908facf
Timestamp: 1700812907 Timestamp [UCT]: 2023-11-24 08:01:47 Age [y:d:h:m:s]: 01:069:02:38:35
Block: 898485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310534 RingCT/type: yes/0
Extra: 0120f1c7995c6440e550e0e92650d517a9d53b7af21bfa5e37d9e28e5eb908facf02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.647062456000 dcy

stealth address amount amount idx
00: 4c830cf7e257c6be209a44b0d7d8b932089be899965f8fa8afa46b01ce78d971 0.647062456000 1354904 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": 898495, "vin": [ { "gen": { "height": 898485 } } ], "vout": [ { "amount": 647062456, "target": { "key": "4c830cf7e257c6be209a44b0d7d8b932089be899965f8fa8afa46b01ce78d971" } } ], "extra": [ 1, 32, 241, 199, 153, 92, 100, 64, 229, 80, 224, 233, 38, 80, 213, 23, 169, 213, 59, 122, 242, 27, 250, 94, 55, 217, 226, 142, 94, 185, 8, 250, 207, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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