Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4538cbdb15806d06b836e50a983f85c77096ecb86685a4c7c4eef143b68422

Tx prefix hash: f0ddb3b7517243d051740010642aaa43f8b81a83f4f77e5c1c25a2ee489229d7
Tx public key: acffb50f841352e9244c5e31c68267fb4e47bff7f30ae666bef1a55674e300f0
Timestamp: 1699565297 Timestamp [UCT]: 2023-11-09 21:28:17 Age [y:d:h:m:s]: 01:004:01:04:48
Block: 888147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264250 RingCT/type: yes/0
Extra: 01acffb50f841352e9244c5e31c68267fb4e47bff7f30ae666bef1a55674e300f0021100000008faf35c9c000000000000000000

1 output(s) for total of 0.700164847000 dcy

stealth address amount amount idx
00: 4765c8385bd596840f7faa2175a4a37083e8625556332f7fd07dae1994c181f7 0.700164847000 1344072 of 0

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": 888157, "vin": [ { "gen": { "height": 888147 } } ], "vout": [ { "amount": 700164847, "target": { "key": "4765c8385bd596840f7faa2175a4a37083e8625556332f7fd07dae1994c181f7" } } ], "extra": [ 1, 172, 255, 181, 15, 132, 19, 82, 233, 36, 76, 94, 49, 198, 130, 103, 251, 78, 71, 191, 247, 243, 10, 230, 102, 190, 241, 165, 86, 116, 227, 0, 240, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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