Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 004fc3d7722dfd81e897ecf9a6c5d794d65504cacb58ec7a5d54955663276b4f

Tx prefix hash: 753e89751b67c30b7de278ce856c0d1ab7eaf7aa73a78dbef17d6b0dcd8c0dfa
Tx public key: 384970fd45eb59048cb2168d57e36698fe7ce2c52fe57ec10abaf89c1e9321b6
Timestamp: 1614056707 Timestamp [UCT]: 2021-02-23 05:05:07 Age [y:d:h:m:s]: 04:251:11:38:14
Block: 204741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197315 RingCT/type: yes/0
Extra: 01384970fd45eb59048cb2168d57e36698fe7ce2c52fe57ec10abaf89c1e9321b602110000000aece3035d000000000000000000

1 output(s) for total of 128.708933341000 dcy

stealth address amount amount idx
00: 7f47c3e774965e449e224ee0cc778907440aa55bcced23f702f86f894f1b49b3 128.708933341000 418413 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": 204751, "vin": [ { "gen": { "height": 204741 } } ], "vout": [ { "amount": 128708933341, "target": { "key": "7f47c3e774965e449e224ee0cc778907440aa55bcced23f702f86f894f1b49b3" } } ], "extra": [ 1, 56, 73, 112, 253, 69, 235, 89, 4, 140, 178, 22, 141, 87, 227, 102, 152, 254, 124, 226, 197, 47, 229, 126, 193, 10, 186, 248, 156, 30, 147, 33, 182, 2, 17, 0, 0, 0, 10, 236, 227, 3, 93, 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