Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 453ac4faf933202261d749d314a144f12d085b2f1953b51fbcf7121b92ba5979

Tx prefix hash: ab531f6d10fee30f554f984c043a1c550fc28a08c5fcd311751e17cb87f70f2c
Tx public key: 6a27f8f8f59e33deefab54b8f5b656b7663bd7cef9895fd129e4bbaf8dbf4117
Timestamp: 1736355487 Timestamp [UCT]: 2025-01-08 16:58:07 Age [y:d:h:m:s]: 00:163:01:23:04
Block: 1193010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116208 RingCT/type: yes/0
Extra: 016a27f8f8f59e33deefab54b8f5b656b7663bd7cef9895fd129e4bbaf8dbf41170211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fdec182dd85fc978f05d0c4a66cb131e61b63959403133f0bbe213087e05bc3 0.600000000000 1679567 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": 1193020, "vin": [ { "gen": { "height": 1193010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fdec182dd85fc978f05d0c4a66cb131e61b63959403133f0bbe213087e05bc3" } } ], "extra": [ 1, 106, 39, 248, 248, 245, 158, 51, 222, 239, 171, 84, 184, 245, 182, 86, 183, 102, 59, 215, 206, 249, 137, 95, 209, 41, 228, 187, 175, 141, 191, 65, 23, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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