Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed935c0b28c6b5032e23eabe65cac10fbd224bc998a8689bcf9638801e6e3263

Tx prefix hash: f0fc874e5c11ee8baabba764e94728bd290997a0b543f04370e8c13d7e384a5f
Tx public key: bb397198c23bd3ff288fdc1aa9d40515ba661259a1277f80a3e7351c01840d0f
Timestamp: 1711143477 Timestamp [UCT]: 2024-03-22 21:37:57 Age [y:d:h:m:s]: 01:017:01:24:46
Block: 984154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273137 RingCT/type: yes/0
Extra: 01bb397198c23bd3ff288fdc1aa9d40515ba661259a1277f80a3e7351c01840d0f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fea11b53f8f692cbe9b1e3c43183041017558eea27891656ba051b1d5cdb94d2 0.600000000000 1444315 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": 984164, "vin": [ { "gen": { "height": 984154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fea11b53f8f692cbe9b1e3c43183041017558eea27891656ba051b1d5cdb94d2" } } ], "extra": [ 1, 187, 57, 113, 152, 194, 59, 211, 255, 40, 143, 220, 26, 169, 212, 5, 21, 186, 102, 18, 89, 161, 39, 127, 128, 163, 231, 53, 28, 1, 132, 13, 15, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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