Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536e0a2751c9578c353bf8ae3e4a736de3c11264e385ac7aef0ee86fb36459cb

Tx prefix hash: 3b4b0ff823eb54b36b3a87ce6b2274bc04aa312e8fc6ca7bc571cb40225affac
Tx public key: 87d01eb5f162ce54441019c25c031399499c4ca6c674336814c87adaf788389d
Timestamp: 1669470973 Timestamp [UCT]: 2022-11-26 13:56:13 Age [y:d:h:m:s]: 02:143:17:58:35
Block: 639539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 624466 RingCT/type: yes/0
Extra: 0187d01eb5f162ce54441019c25c031399499c4ca6c674336814c87adaf788389d021100000001faf35c9c000000000000000000

1 output(s) for total of 4.665968576000 dcy

stealth address amount amount idx
00: 6ba0da575edf101fc9bb4ed076ac801a4bb1e933e8a5d5e876bbd475d90f5be6 4.665968576000 1079198 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": 639549, "vin": [ { "gen": { "height": 639539 } } ], "vout": [ { "amount": 4665968576, "target": { "key": "6ba0da575edf101fc9bb4ed076ac801a4bb1e933e8a5d5e876bbd475d90f5be6" } } ], "extra": [ 1, 135, 208, 30, 181, 241, 98, 206, 84, 68, 16, 25, 194, 92, 3, 19, 153, 73, 156, 76, 166, 198, 116, 51, 104, 20, 200, 122, 218, 247, 136, 56, 157, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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