Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d43ee976a1dd507536d8c164e1eb00543847c109e248657968cce7a8fc94f7a

Tx prefix hash: ec194509de7e80bdf06b06a940a9837811826cb14354ff2c0e7d453c8421ef4a
Tx public key: e5e86fcc415d00af8d7af5a4e0cc4800b7770ae15d4b27c69eec77f39daa4007
Timestamp: 1636061699 Timestamp [UCT]: 2021-11-04 21:34:59 Age [y:d:h:m:s]: 03:130:09:32:27
Block: 367439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871515 RingCT/type: yes/0
Extra: 01e5e86fcc415d00af8d7af5a4e0cc4800b7770ae15d4b27c69eec77f39daa40070211000000166a2c97e6000000000000000000

1 output(s) for total of 37.198245801000 dcy

stealth address amount amount idx
00: 13371204480b420079a04663dc20e38a90a8f44c4a0664190fdbc843381d5646 37.198245801000 745571 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": 367449, "vin": [ { "gen": { "height": 367439 } } ], "vout": [ { "amount": 37198245801, "target": { "key": "13371204480b420079a04663dc20e38a90a8f44c4a0664190fdbc843381d5646" } } ], "extra": [ 1, 229, 232, 111, 204, 65, 93, 0, 175, 141, 122, 245, 164, 224, 204, 72, 0, 183, 119, 10, 225, 93, 75, 39, 198, 158, 236, 119, 243, 157, 170, 64, 7, 2, 17, 0, 0, 0, 22, 106, 44, 151, 230, 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