Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0963e2fac1ad01d0c5b0b00ecee21969902f424b1d01dbf72da45d7356fe8d3b

Tx prefix hash: bca891e14f589eef1cb07a9dc0c8aef15cc524e1d11dbed4ee960e83d8ad64e2
Tx public key: 9fcd65da7be935e3f7184fc28021abd2bd2ea22593b3fcf80857e72429ec1cae
Timestamp: 1745384036 Timestamp [UCT]: 2025-04-23 04:53:56 Age [y:d:h:m:s]: 00:275:01:17:08
Block: 1267487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194253 RingCT/type: yes/0
Extra: 019fcd65da7be935e3f7184fc28021abd2bd2ea22593b3fcf80857e72429ec1cae021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d45d9fa70841a89aecc73121e21b6ff618fb9b0c6890232eef5520153d88011 0.600000000000 1754716 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": 1267497, "vin": [ { "gen": { "height": 1267487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d45d9fa70841a89aecc73121e21b6ff618fb9b0c6890232eef5520153d88011" } } ], "extra": [ 1, 159, 205, 101, 218, 123, 233, 53, 227, 247, 24, 79, 194, 128, 33, 171, 210, 189, 46, 162, 37, 147, 179, 252, 248, 8, 87, 231, 36, 41, 236, 28, 174, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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