Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b2c732718c910563c17c9c540761a935ddcd097a3651b87c8202a6ffece661c

Tx prefix hash: c9409a2f15d96607a573eab742913af520c71e3e1fe1fe1d3485a7368b64a0c7
Tx public key: 7ba67de04d4fa828420e5d9a9c9aa365d7dfdb30b23c04405455a261c823237f
Timestamp: 1725629516 Timestamp [UCT]: 2024-09-06 13:31:56 Age [y:d:h:m:s]: 00:281:09:12:53
Block: 1104230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200905 RingCT/type: yes/0
Extra: 017ba67de04d4fa828420e5d9a9c9aa365d7dfdb30b23c04405455a261c823237f021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fad7954bf9a06a9bd5f7af9c7977ff440054ba56a4b106956aa6446effb1c860 0.600000000000 1581309 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": 1104240, "vin": [ { "gen": { "height": 1104230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fad7954bf9a06a9bd5f7af9c7977ff440054ba56a4b106956aa6446effb1c860" } } ], "extra": [ 1, 123, 166, 125, 224, 77, 79, 168, 40, 66, 14, 93, 154, 156, 154, 163, 101, 215, 223, 219, 48, 178, 60, 4, 64, 84, 85, 162, 97, 200, 35, 35, 127, 2, 17, 0, 0, 0, 16, 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