Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12133e84b743473407e606762272f94efa5553552a59741e364cd162ef38b6e6

Tx prefix hash: ac9730309eba6f392f173f829e7c7e69d2d99d74b3e6d01839bda13e28d0f6f2
Tx public key: 7ef9721e279534a3e0f3e1a7dc72843dacc56d07dd98ab50793592a6293b270f
Timestamp: 1710686853 Timestamp [UCT]: 2024-03-17 14:47:33 Age [y:d:h:m:s]: 00:240:20:14:19
Block: 980363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172409 RingCT/type: yes/0
Extra: 017ef9721e279534a3e0f3e1a7dc72843dacc56d07dd98ab50793592a6293b270f021100000003a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42a147d1453bad10a1a0cdcbaa7deac46727c4840c0595cd89bafb53d57ad5b7 0.600000000000 1440428 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": 980373, "vin": [ { "gen": { "height": 980363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42a147d1453bad10a1a0cdcbaa7deac46727c4840c0595cd89bafb53d57ad5b7" } } ], "extra": [ 1, 126, 249, 114, 30, 39, 149, 52, 163, 224, 243, 225, 167, 220, 114, 132, 61, 172, 197, 109, 7, 221, 152, 171, 80, 121, 53, 146, 166, 41, 59, 39, 15, 2, 17, 0, 0, 0, 3, 165, 223, 157, 134, 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