Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9bbf4a1b38bc555ab6a2053c2cccbb67e7159435abb3b29d1c8cb6487f5d235

Tx prefix hash: 73eaf38f321b74bb9246340608c0ca511d5678ffef83485577ea6a243bc64a6a
Tx public key: fc317aef8a7e6a941c7e143c85860e167bb52ce2f7b1bf15f3ad80d4f1fac2bd
Timestamp: 1676545792 Timestamp [UCT]: 2023-02-16 11:09:52 Age [y:d:h:m:s]: 02:111:16:07:56
Block: 698180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601450 RingCT/type: yes/0
Extra: 01fc317aef8a7e6a941c7e143c85860e167bb52ce2f7b1bf15f3ad80d4f1fac2bd02110000000174b6d784000000000000000000

1 output(s) for total of 2.982907236000 dcy

stealth address amount amount idx
00: be1da7163311761d4ea594e414224088d5f55cafa78831566c3caca1ec85ceb2 2.982907236000 1141469 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": 698190, "vin": [ { "gen": { "height": 698180 } } ], "vout": [ { "amount": 2982907236, "target": { "key": "be1da7163311761d4ea594e414224088d5f55cafa78831566c3caca1ec85ceb2" } } ], "extra": [ 1, 252, 49, 122, 239, 138, 126, 106, 148, 28, 126, 20, 60, 133, 134, 14, 22, 123, 181, 44, 226, 247, 177, 191, 21, 243, 173, 128, 212, 241, 250, 194, 189, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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