Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c4492c0f8f3855a5fe3d035a1963da05fa06d4d35ccf45470921334e8495774

Tx prefix hash: c174202784b18f358cfcec993669142b276699fb29a0a8a7e52521e207707d20
Tx public key: c3f734f429d14d56a0747eadc0bfb59629476053ecc3dc586309060cb65b62c3
Timestamp: 1696695337 Timestamp [UCT]: 2023-10-07 16:15:37 Age [y:d:h:m:s]: 01:097:21:29:30
Block: 864556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331222 RingCT/type: yes/0
Extra: 01c3f734f429d14d56a0747eadc0bfb59629476053ecc3dc586309060cb65b62c302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.838237552000 dcy

stealth address amount amount idx
00: a5186ac1273fd6889cdc646509d8ecfbe98b68e6e1a131d8821ac9cd633a4541 0.838237552000 1319072 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": 864566, "vin": [ { "gen": { "height": 864556 } } ], "vout": [ { "amount": 838237552, "target": { "key": "a5186ac1273fd6889cdc646509d8ecfbe98b68e6e1a131d8821ac9cd633a4541" } } ], "extra": [ 1, 195, 247, 52, 244, 41, 209, 77, 86, 160, 116, 126, 173, 192, 191, 181, 150, 41, 71, 96, 83, 236, 195, 220, 88, 99, 9, 6, 12, 182, 91, 98, 195, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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