Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ac3851caeccf1e400943aad14649ca41f71aceaf6e558b22c48773a808dc770

Tx prefix hash: 49d77ce4ebd691a57048afbf25da0c02c455a40fc0170847bb7bf01fe5bae6f5
Tx public key: 81a5e22ab2a23363449d0a4073d7501521e83f3fc4c3d28d6d37e3f03d0a6c54
Timestamp: 1710318644 Timestamp [UCT]: 2024-03-13 08:30:44 Age [y:d:h:m:s]: 01:048:21:03:59
Block: 977301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295916 RingCT/type: yes/0
Extra: 0181a5e22ab2a23363449d0a4073d7501521e83f3fc4c3d28d6d37e3f03d0a6c540211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 619c33f6fdfc777b3039a2349264f0562ef437991f66a76c624ed31c27aacaca 0.600000000000 1437302 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": 977311, "vin": [ { "gen": { "height": 977301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "619c33f6fdfc777b3039a2349264f0562ef437991f66a76c624ed31c27aacaca" } } ], "extra": [ 1, 129, 165, 226, 42, 178, 162, 51, 99, 68, 157, 10, 64, 115, 215, 80, 21, 33, 232, 63, 63, 196, 195, 210, 141, 109, 55, 227, 240, 61, 10, 108, 84, 2, 17, 0, 0, 0, 8, 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