Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62a3ffdc076289343fe51ae0224d2b067bd1508c2e05ec71c3da8c392fc3caad

Tx prefix hash: 3779ed89af9fee0cc55ccfc9caa4a703e190af872fbdd7b3fb67f09b0c181734
Tx public key: 57fdedd7447c18aea8eb0dfd02869ba2eeb7cbc73a4764e7339906d7c63ff17e
Timestamp: 1722246065 Timestamp [UCT]: 2024-07-29 09:41:05 Age [y:d:h:m:s]: 00:248:15:39:09
Block: 1076183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177607 RingCT/type: yes/0
Extra: 0157fdedd7447c18aea8eb0dfd02869ba2eeb7cbc73a4764e7339906d7c63ff17e021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91745e4a869eee813e0ff0314981d55742da306227c3fce72e70d09eeabfa9e7 0.600000000000 1548718 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": 1076193, "vin": [ { "gen": { "height": 1076183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91745e4a869eee813e0ff0314981d55742da306227c3fce72e70d09eeabfa9e7" } } ], "extra": [ 1, 87, 253, 237, 215, 68, 124, 24, 174, 168, 235, 13, 253, 2, 134, 155, 162, 238, 183, 203, 199, 58, 71, 100, 231, 51, 153, 6, 215, 198, 63, 241, 126, 2, 17, 0, 0, 0, 6, 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