Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84e8dac46b52f3f8152d8e1f8c0caddec7d87c8f908184239446a3a9bf34cacf

Tx prefix hash: 9f13172d98c6b4ae5ea24bb27a20c81ea23294e77f3cb02f86c76d4502b8a175
Tx public key: d2db61da60f0e9cd36863564c0c2130c215bc4a1b09750b1ae1288edd5c14543
Timestamp: 1726467567 Timestamp [UCT]: 2024-09-16 06:19:27 Age [y:d:h:m:s]: 00:221:12:30:12
Block: 1111171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158167 RingCT/type: yes/0
Extra: 01d2db61da60f0e9cd36863564c0c2130c215bc4a1b09750b1ae1288edd5c14543021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f22c340a2556c3dc86f9a658a54f428374089898c75fda4f3af4924f41d96393 0.600000000000 1590038 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": 1111181, "vin": [ { "gen": { "height": 1111171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f22c340a2556c3dc86f9a658a54f428374089898c75fda4f3af4924f41d96393" } } ], "extra": [ 1, 210, 219, 97, 218, 96, 240, 233, 205, 54, 134, 53, 100, 192, 194, 19, 12, 33, 91, 196, 161, 176, 151, 80, 177, 174, 18, 136, 237, 213, 193, 69, 67, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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