Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dd289359737e07db6067ff01a1817f442a401dc12d1a5d0bbead6c353181d33

Tx prefix hash: 963183d1d535b78b7e6fa91519d9019c9c370ed236657df799eecbc63613deec
Tx public key: 06dbbc051ec0f71a8a0b0c011a1af4245169f880c0d2f994d5447d1c5974f212
Timestamp: 1730118662 Timestamp [UCT]: 2024-10-28 12:31:02 Age [y:d:h:m:s]: 00:161:17:55:53
Block: 1141368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115425 RingCT/type: yes/0
Extra: 0106dbbc051ec0f71a8a0b0c011a1af4245169f880c0d2f994d5447d1c5974f212021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 351d1f8a1143f547bf6e6c0401b8edec15084c43026c7dc540efd3d139ccacbe 0.600000000000 1625175 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": 1141378, "vin": [ { "gen": { "height": 1141368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "351d1f8a1143f547bf6e6c0401b8edec15084c43026c7dc540efd3d139ccacbe" } } ], "extra": [ 1, 6, 219, 188, 5, 30, 192, 247, 26, 138, 11, 12, 1, 26, 26, 244, 36, 81, 105, 248, 128, 192, 210, 249, 148, 213, 68, 125, 28, 89, 116, 242, 18, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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