Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9f9e2d5537ab3f98502006f6bdff2b48970e444e66e5ab95e0425bfee80ae30

Tx prefix hash: 9211cf144f4ba7704af4d2b9bdbba8af78943845a5a5179f1f735d3da8caafb0
Tx public key: dae4c06f35ce4ef2ce4e1edc5788b097d9547ab69f44ab1898a9a71f0f140860
Timestamp: 1725834506 Timestamp [UCT]: 2024-09-08 22:28:26 Age [y:d:h:m:s]: 00:167:15:27:09
Block: 1105922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119615 RingCT/type: yes/0
Extra: 01dae4c06f35ce4ef2ce4e1edc5788b097d9547ab69f44ab1898a9a71f0f140860021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f46f8d0886c734b9f069432382feee7575260d6aeefe6ba3120c5492af23e8e 0.600000000000 1583433 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": 1105932, "vin": [ { "gen": { "height": 1105922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f46f8d0886c734b9f069432382feee7575260d6aeefe6ba3120c5492af23e8e" } } ], "extra": [ 1, 218, 228, 192, 111, 53, 206, 78, 242, 206, 78, 30, 220, 87, 136, 176, 151, 217, 84, 122, 182, 159, 68, 171, 24, 152, 169, 167, 31, 15, 20, 8, 96, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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