Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df856cd1ee09aee502b64fb0a84351bb0c2d1bd6a084a981dc15287255f66e25

Tx prefix hash: c41f9d736f88675d81c18abe6235b2f5e4bb9a69b75603681a038d85f983eb5f
Tx public key: 6f79c77235e349c13052fee0abe0f9c446f1bff4dd4b5736342218d00bff64d4
Timestamp: 1702644921 Timestamp [UCT]: 2023-12-15 12:55:21 Age [y:d:h:m:s]: 01:036:04:11:09
Block: 913668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287179 RingCT/type: yes/0
Extra: 016f79c77235e349c13052fee0abe0f9c446f1bff4dd4b5736342218d00bff64d402110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d7efaee1afe156d32ebe57345204ff6a404c948089be1f7c88d7a54acdc24fd 0.600000000000 1370944 of 15

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": 913678, "vin": [ { "gen": { "height": 913668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d7efaee1afe156d32ebe57345204ff6a404c948089be1f7c88d7a54acdc24fd" } } ], "extra": [ 1, 111, 121, 199, 114, 53, 227, 73, 193, 48, 82, 254, 224, 171, 224, 249, 196, 70, 241, 191, 244, 221, 75, 87, 54, 52, 34, 24, 208, 11, 255, 100, 212, 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