Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 829f3a6386f613d546e6d26c2b53687fbb4c9b0801d880229c5666253158fddc

Tx prefix hash: 156dd200136e9bf83002016fe5c2a3260249a8ba2fee193df351a8b30b81a9a2
Tx public key: e07ec10155a7adc8ab11b52f5d77d3c633b6f35ebd28fa27844c912b0ae449d4
Timestamp: 1738089443 Timestamp [UCT]: 2025-01-28 18:37:23 Age [y:d:h:m:s]: 00:140:11:26:09
Block: 1207118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100345 RingCT/type: yes/0
Extra: 01e07ec10155a7adc8ab11b52f5d77d3c633b6f35ebd28fa27844c912b0ae449d4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc60afac9b052e2ac233c69c8d0da7a7eebd029cf1b03a34cbed61bf367df35d 0.600000000000 1693839 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": 1207128, "vin": [ { "gen": { "height": 1207118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc60afac9b052e2ac233c69c8d0da7a7eebd029cf1b03a34cbed61bf367df35d" } } ], "extra": [ 1, 224, 126, 193, 1, 85, 167, 173, 200, 171, 17, 181, 47, 93, 119, 211, 198, 51, 182, 243, 94, 189, 40, 250, 39, 132, 76, 145, 43, 10, 228, 73, 212, 2, 17, 0, 0, 0, 3, 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