Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de997e5425e5837c197227923045bf3951a5d74b603823f2707586ac342e8cae

Tx prefix hash: 4eda1ffbeb350ad064e05dffdae5e60e02ffddb392280f58b9e814c1c15edffd
Tx public key: f867d1e918a85248be894214c8e0547b3100fdd8f5cfb2e54c0c6224eede1ef9
Timestamp: 1581866850 Timestamp [UCT]: 2020-02-16 15:27:30 Age [y:d:h:m:s]: 04:358:23:51:38
Block: 66247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148628 RingCT/type: yes/0
Extra: 01f867d1e918a85248be894214c8e0547b3100fdd8f5cfb2e54c0c6224eede1ef9021100000007d81c26c0000000000000000000

1 output(s) for total of 370.251645857000 dcy

stealth address amount amount idx
00: a4c64c29c1979872c21cc36ec5a9e0740bfd785b2b771d6c74164107835b8cdb 370.251645857000 122036 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": 66257, "vin": [ { "gen": { "height": 66247 } } ], "vout": [ { "amount": 370251645857, "target": { "key": "a4c64c29c1979872c21cc36ec5a9e0740bfd785b2b771d6c74164107835b8cdb" } } ], "extra": [ 1, 248, 103, 209, 233, 24, 168, 82, 72, 190, 137, 66, 20, 200, 224, 84, 123, 49, 0, 253, 216, 245, 207, 178, 229, 76, 12, 98, 36, 238, 222, 30, 249, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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