Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf74b4070bcb81b1f053b142ccedf4c1b40d73982437767613e169d885eeacf5

Tx prefix hash: f9b559aa65d7b70eafdcf53882f4e0219cb1ad3cf61ee69364185be1a14b1489
Tx public key: 40bc484c5cdfec8c6fe219eee19fb4f3bf44ee6633fb8419f88c0d40f53a673a
Timestamp: 1717748129 Timestamp [UCT]: 2024-06-07 08:15:29 Age [y:d:h:m:s]: 00:335:02:51:26
Block: 1038895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239513 RingCT/type: yes/0
Extra: 0140bc484c5cdfec8c6fe219eee19fb4f3bf44ee6633fb8419f88c0d40f53a673a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e9a17d03eeefc510418392e668aa679c8d595b322b48de0ccd270622a47a71 0.600000000000 1507462 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": 1038905, "vin": [ { "gen": { "height": 1038895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e9a17d03eeefc510418392e668aa679c8d595b322b48de0ccd270622a47a71" } } ], "extra": [ 1, 64, 188, 72, 76, 92, 223, 236, 140, 111, 226, 25, 238, 225, 159, 180, 243, 191, 68, 238, 102, 51, 251, 132, 25, 248, 140, 13, 64, 245, 58, 103, 58, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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