Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 886abdd4c1cea4b8cb1082bb43c8091e09f8f56a01a50d87309fc8879695d63a

Tx prefix hash: 5d14ecf9d78d82467fe9c5d489258066d1c572992f8dc011d4ae5632a2a8616e
Tx public key: a2b1caead6666023dcaf40af11596a76e1be04504814fdb7b193bf9ba43d877e
Timestamp: 1735148724 Timestamp [UCT]: 2024-12-25 17:45:24 Age [y:d:h:m:s]: 00:313:15:15:51
Block: 1183032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221654 RingCT/type: yes/0
Extra: 01a2b1caead6666023dcaf40af11596a76e1be04504814fdb7b193bf9ba43d877e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 606cd0f82b6dcbd95aeb752bfd59b4078075ad7b0324dd9fb2506fbc5550dde8 0.600000000000 1669471 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": 1183042, "vin": [ { "gen": { "height": 1183032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "606cd0f82b6dcbd95aeb752bfd59b4078075ad7b0324dd9fb2506fbc5550dde8" } } ], "extra": [ 1, 162, 177, 202, 234, 214, 102, 96, 35, 220, 175, 64, 175, 17, 89, 106, 118, 225, 190, 4, 80, 72, 20, 253, 183, 177, 147, 191, 155, 164, 61, 135, 126, 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