Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76509292283212c96939ee3edcb139afb213b8630c454b0e9a57a4bfa0ec78cf

Tx prefix hash: d1c41432bc689e276e56fb87880c8fa9d5a7e51d40c7f4062012815b81b72adf
Tx public key: 78ebabc019e0ca5c73520c2bc73ce83d97eba71be863a9dd5c422e1bbed5a88b
Timestamp: 1733380706 Timestamp [UCT]: 2024-12-05 06:38:26 Age [y:d:h:m:s]: 00:196:05:37:32
Block: 1168383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139952 RingCT/type: yes/0
Extra: 0178ebabc019e0ca5c73520c2bc73ce83d97eba71be863a9dd5c422e1bbed5a88b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 599c34912759e47214327c3299c7172ae9483fd8da45c3cfa27142d1d7c0e746 0.600000000000 1654092 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": 1168393, "vin": [ { "gen": { "height": 1168383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "599c34912759e47214327c3299c7172ae9483fd8da45c3cfa27142d1d7c0e746" } } ], "extra": [ 1, 120, 235, 171, 192, 25, 224, 202, 92, 115, 82, 12, 43, 199, 60, 232, 61, 151, 235, 167, 27, 232, 99, 169, 221, 92, 66, 46, 27, 190, 213, 168, 139, 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