Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cfe782cae88e112847f5f869e214dd5e956addc993d07169d1a4453dfee53e4

Tx prefix hash: 4c6c98d7d4c5ffa470b6f289a426fe39f3fc7d620b88f7b39688c476be256367
Tx public key: 2445fd97ab0e55db29880e0fe71c5a6172ffc17ea397f71be03c95526f7034d9
Timestamp: 1713013747 Timestamp [UCT]: 2024-04-13 13:09:07 Age [y:d:h:m:s]: 00:213:21:37:38
Block: 999619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153142 RingCT/type: yes/0
Extra: 012445fd97ab0e55db29880e0fe71c5a6172ffc17ea397f71be03c95526f7034d90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4306a55433137f92d2bae219566343283d064e5b93472d8c037613a7dfb8e0a7 0.600000000000 1460101 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": 999629, "vin": [ { "gen": { "height": 999619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4306a55433137f92d2bae219566343283d064e5b93472d8c037613a7dfb8e0a7" } } ], "extra": [ 1, 36, 69, 253, 151, 171, 14, 85, 219, 41, 136, 14, 15, 231, 28, 90, 97, 114, 255, 193, 126, 163, 151, 247, 27, 224, 60, 149, 82, 111, 112, 52, 217, 2, 17, 0, 0, 0, 1, 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