Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 684ea5158d26b88c46d7c575663c21bd18b77ebefcf522627a96cd97915c18fb

Tx prefix hash: b8d9652b459954faa93933423d12331ed300d0b1ea3cbc0e6b52ce890e90c80b
Tx public key: ea8c2fd373450d63ba1a3e84dc46f881a4d4ca3484691a86c3e99810cd9e80e2
Timestamp: 1717076940 Timestamp [UCT]: 2024-05-30 13:49:00 Age [y:d:h:m:s]: 00:314:16:22:38
Block: 1033321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224907 RingCT/type: yes/0
Extra: 01ea8c2fd373450d63ba1a3e84dc46f881a4d4ca3484691a86c3e99810cd9e80e202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d10031e1503b7c4f68cd5283e5ab66a3c4553cbeabeadd71773514dfa6db8720 0.600000000000 1501786 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": 1033331, "vin": [ { "gen": { "height": 1033321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d10031e1503b7c4f68cd5283e5ab66a3c4553cbeabeadd71773514dfa6db8720" } } ], "extra": [ 1, 234, 140, 47, 211, 115, 69, 13, 99, 186, 26, 62, 132, 220, 70, 248, 129, 164, 212, 202, 52, 132, 105, 26, 134, 195, 233, 152, 16, 205, 158, 128, 226, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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