Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 638b509797537bda0cccdd6e7331c69224c2ce55aec87f2bfbcff6739a75d899

Tx prefix hash: 1f76ea244be9b85bf882bab2b26248174b64271274a122fa3c61749398b57f44
Tx public key: 7b450e2830ba0ac84880881cc66a6ef01aaf60bc12edcdfb0b1b0e01c80f9f8f
Timestamp: 1669488516 Timestamp [UCT]: 2022-11-26 18:48:36 Age [y:d:h:m:s]: 02:075:00:09:57
Block: 639686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575297 RingCT/type: yes/0
Extra: 017b450e2830ba0ac84880881cc66a6ef01aaf60bc12edcdfb0b1b0e01c80f9f8f021100000005faf35c9c000000000000000000

1 output(s) for total of 4.660738507000 dcy

stealth address amount amount idx
00: efbe473a6dce468d545e95f94eb30a1e87a8dcc0e2c6d729e243ade0e7f353bd 4.660738507000 1079355 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": 639696, "vin": [ { "gen": { "height": 639686 } } ], "vout": [ { "amount": 4660738507, "target": { "key": "efbe473a6dce468d545e95f94eb30a1e87a8dcc0e2c6d729e243ade0e7f353bd" } } ], "extra": [ 1, 123, 69, 14, 40, 48, 186, 10, 200, 72, 128, 136, 28, 198, 106, 110, 240, 26, 175, 96, 188, 18, 237, 205, 251, 11, 27, 14, 1, 200, 15, 159, 143, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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