Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 041476a9136c4aa2202c3641c13f52a7549f8ceed82003536ba1ba6f4a213e88

Tx prefix hash: a76abd3a08f2ade11188c35f1a753fcb446664027a79dff0c462afdc861d5c47
Tx public key: 062692984558ec44f1598c86b9dcef4bbaf6e82a0aeaa5fc1583abd7aafd1546
Timestamp: 1720809097 Timestamp [UCT]: 2024-07-12 18:31:37 Age [y:d:h:m:s]: 01:125:02:48:28
Block: 1064273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347937 RingCT/type: yes/0
Extra: 01062692984558ec44f1598c86b9dcef4bbaf6e82a0aeaa5fc1583abd7aafd1546021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5829efe9f6fdc88f02a451147faa3c011add49e529bc6b158fc6a965d061732 0.600000000000 1534796 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": 1064283, "vin": [ { "gen": { "height": 1064273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5829efe9f6fdc88f02a451147faa3c011add49e529bc6b158fc6a965d061732" } } ], "extra": [ 1, 6, 38, 146, 152, 69, 88, 236, 68, 241, 89, 140, 134, 185, 220, 239, 75, 186, 246, 232, 42, 10, 234, 165, 252, 21, 131, 171, 215, 170, 253, 21, 70, 2, 17, 0, 0, 0, 1, 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