Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 208297e29c175d1123c2b64f4960dd5a0618ebbafc4e30f0c2efa82b74d4f1b3

Tx prefix hash: e7410cade7521a65f6093f3a10b2703ac256fcf58de33107c37da877f5d7fe6a
Tx public key: 8819ab41a4d7ed15b9050b7ed48df8e2e387c207f9f20ae5595de82e2f8c252d
Timestamp: 1696447653 Timestamp [UCT]: 2023-10-04 19:27:33 Age [y:d:h:m:s]: 01:176:22:25:20
Block: 862497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387497 RingCT/type: yes/0
Extra: 018819ab41a4d7ed15b9050b7ed48df8e2e387c207f9f20ae5595de82e2f8c252d021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.851509383000 dcy

stealth address amount amount idx
00: 3af03a66b58e03c1c7a005c442ce8a6e4d2ce8cf49c691d2dc45749e9cf3e42d 0.851509383000 1316919 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": 862507, "vin": [ { "gen": { "height": 862497 } } ], "vout": [ { "amount": 851509383, "target": { "key": "3af03a66b58e03c1c7a005c442ce8a6e4d2ce8cf49c691d2dc45749e9cf3e42d" } } ], "extra": [ 1, 136, 25, 171, 65, 164, 215, 237, 21, 185, 5, 11, 126, 212, 141, 248, 226, 227, 135, 194, 7, 249, 242, 10, 229, 89, 93, 232, 46, 47, 140, 37, 45, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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