Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6db728eebfa46a68c03e783fc2089155c2d3b5fd446603bac575d671d0a3e410

Tx prefix hash: ea4e2eac1233b4b48067f624b068ea67b284cf3373be2dc9ed18add8887acbb9
Tx public key: 3359c4f17395432b0047de509ad675c6cf7bfcb7ca15a8f2fbeb265519f7d32c
Timestamp: 1739681728 Timestamp [UCT]: 2025-02-16 04:55:28 Age [y:d:h:m:s]: 00:277:17:32:31
Block: 1220255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196275 RingCT/type: yes/0
Extra: 013359c4f17395432b0047de509ad675c6cf7bfcb7ca15a8f2fbeb265519f7d32c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 662b4139895854896c2d8e2382f78dd240a156b6ddd6582973d717cee658f208 0.600000000000 1707092 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": 1220265, "vin": [ { "gen": { "height": 1220255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "662b4139895854896c2d8e2382f78dd240a156b6ddd6582973d717cee658f208" } } ], "extra": [ 1, 51, 89, 196, 241, 115, 149, 67, 43, 0, 71, 222, 80, 154, 214, 117, 198, 207, 123, 252, 183, 202, 21, 168, 242, 251, 235, 38, 85, 25, 247, 211, 44, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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