Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37a21cc195be2e595b1d9e3f5d54fa9b60b712ace0afeabdfa927013484a8037

Tx prefix hash: 6e669f8d075ce856a0d8b63ad360651e6dd8538113fc966da87f49aa44e04443
Tx public key: 6cea5e341b5df6d41a223f449c5b11c5d0d43fd301363073b91f23f64773ab36
Timestamp: 1716038870 Timestamp [UCT]: 2024-05-18 13:27:50 Age [y:d:h:m:s]: 00:324:09:34:27
Block: 1024723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231851 RingCT/type: yes/0
Extra: 016cea5e341b5df6d41a223f449c5b11c5d0d43fd301363073b91f23f64773ab3602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4b22503a7aec142f6eb14ac334ae848e584bc39718cf8eb6ad4899b3d3358f6 0.600000000000 1490690 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": 1024733, "vin": [ { "gen": { "height": 1024723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4b22503a7aec142f6eb14ac334ae848e584bc39718cf8eb6ad4899b3d3358f6" } } ], "extra": [ 1, 108, 234, 94, 52, 27, 93, 246, 212, 26, 34, 63, 68, 156, 91, 17, 197, 208, 212, 63, 211, 1, 54, 48, 115, 185, 31, 35, 246, 71, 115, 171, 54, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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