Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89ac3321b2a5f7799fed0428c9f873125f2dc70c9bee6c4def36925606d2ab42

Tx prefix hash: 0dfd1c49589977fdd92cd9bfb8811b17ef35786e84807f2479a214fe70f163c3
Tx public key: 958ca7e82cefa0a5bee056b3d65f2274bca262fddc85a1e688e5557c1eb6a8fc
Timestamp: 1733307437 Timestamp [UCT]: 2024-12-04 10:17:17 Age [y:d:h:m:s]: 00:353:07:59:13
Block: 1167779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250059 RingCT/type: yes/0
Extra: 01958ca7e82cefa0a5bee056b3d65f2274bca262fddc85a1e688e5557c1eb6a8fc0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66dbaaeadcfcefa326eeefc4a5ab5a213872cc8019f3ebf7606eb074148c37e8 0.600000000000 1653482 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": 1167789, "vin": [ { "gen": { "height": 1167779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66dbaaeadcfcefa326eeefc4a5ab5a213872cc8019f3ebf7606eb074148c37e8" } } ], "extra": [ 1, 149, 140, 167, 232, 44, 239, 160, 165, 190, 224, 86, 179, 214, 95, 34, 116, 188, 162, 98, 253, 220, 133, 161, 230, 136, 229, 85, 124, 30, 182, 168, 252, 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