Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dfd07ffb887249f5b234b6bfd7f8018080d1c6e1730871ae424ecde63c8dd79

Tx prefix hash: 476d76df4413a09449a41e820e216e6d5489145806efe639fb630b09c986a278
Tx public key: 7e894dcf681bf8c9ddce30fc22c8ba54f591834ec8a9a2c3586976b06e8d6d1c
Timestamp: 1730319286 Timestamp [UCT]: 2024-10-30 20:14:46 Age [y:d:h:m:s]: 00:083:08:46:44
Block: 1143034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59593 RingCT/type: yes/0
Extra: 017e894dcf681bf8c9ddce30fc22c8ba54f591834ec8a9a2c3586976b06e8d6d1c02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2d3db8b5ecba22c68eeff0484215dffc09938d0afc51b3698419d78e82e0d1d 0.600000000000 1626891 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": 1143044, "vin": [ { "gen": { "height": 1143034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2d3db8b5ecba22c68eeff0484215dffc09938d0afc51b3698419d78e82e0d1d" } } ], "extra": [ 1, 126, 137, 77, 207, 104, 27, 248, 201, 221, 206, 48, 252, 34, 200, 186, 84, 245, 145, 131, 78, 200, 169, 162, 195, 88, 105, 118, 176, 110, 141, 109, 28, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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