Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a626e794f1bd73a864caafaff3b38174ccc4f9e46d367e53787b8f6632e3a3ee

Tx prefix hash: 0a8aaac9a5c5137e0f0da9867db93cff9c56f45168271aaa77623e09c3212f19
Tx public key: 6b54776e01c2e920fa42a44f1dde7cd0f2f8222491bf3a4013f71c3b25a0241e
Timestamp: 1734246904 Timestamp [UCT]: 2024-12-15 07:15:04 Age [y:d:h:m:s]: 00:137:08:13:39
Block: 1175573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97958 RingCT/type: yes/0
Extra: 016b54776e01c2e920fa42a44f1dde7cd0f2f8222491bf3a4013f71c3b25a0241e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c05a2b74351ad1f88ce89581cf37cd33bcd14db54b9ca8f004a1f242ec535131 0.600000000000 1661872 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": 1175583, "vin": [ { "gen": { "height": 1175573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c05a2b74351ad1f88ce89581cf37cd33bcd14db54b9ca8f004a1f242ec535131" } } ], "extra": [ 1, 107, 84, 119, 110, 1, 194, 233, 32, 250, 66, 164, 79, 29, 222, 124, 208, 242, 248, 34, 36, 145, 191, 58, 64, 19, 247, 28, 59, 37, 160, 36, 30, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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