Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73263a5af1af59caedef14672d62873e2b9b7d238e1144bc1cdf0e4078b22f42

Tx prefix hash: 5a4abef648df33c66a14abf0138ac0fc35d854a9da6c57a1fe7ac36e87c55be6
Tx public key: 12d8fc9ca0ba75583fd36baa51dc0193698bbb664821ddb405cf0dd76234e7c9
Timestamp: 1703725326 Timestamp [UCT]: 2023-12-28 01:02:06 Age [y:d:h:m:s]: 01:315:07:18:41
Block: 922631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484179 RingCT/type: yes/0
Extra: 0112d8fc9ca0ba75583fd36baa51dc0193698bbb664821ddb405cf0dd76234e7c90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0da5157fd8fd9a9a892445aa0dfa58d1cce955da090232fb44f4bb8f31c8ea64 0.600000000000 1380335 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": 922641, "vin": [ { "gen": { "height": 922631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0da5157fd8fd9a9a892445aa0dfa58d1cce955da090232fb44f4bb8f31c8ea64" } } ], "extra": [ 1, 18, 216, 252, 156, 160, 186, 117, 88, 63, 211, 107, 170, 81, 220, 1, 147, 105, 139, 187, 102, 72, 33, 221, 180, 5, 207, 13, 215, 98, 52, 231, 201, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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