Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cbae2a0a4075bc6aa6f20451805162eb218b3065db4899202fde7cfcfb837fe

Tx prefix hash: fc9452d3eca8a6bb8055d0c46cabbd6a1c6af07a9c2b21665e3b2ec2272b6d61
Tx public key: 50779b06848613dc6660547405e14ea1968271197acb7646255a0439286e0977
Timestamp: 1699359312 Timestamp [UCT]: 2023-11-07 12:15:12 Age [y:d:h:m:s]: 01:151:23:48:09
Block: 886436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369816 RingCT/type: yes/0
Extra: 0150779b06848613dc6660547405e14ea1968271197acb7646255a0439286e09770211000000014b8f5122000000000000000000

1 output(s) for total of 0.709364676000 dcy

stealth address amount amount idx
00: 60d9c2b44ba7c9e3de13843c3f7aa79e47371c9c7f73818fcb6d6b5c79d3f49e 0.709364676000 1342255 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": 886446, "vin": [ { "gen": { "height": 886436 } } ], "vout": [ { "amount": 709364676, "target": { "key": "60d9c2b44ba7c9e3de13843c3f7aa79e47371c9c7f73818fcb6d6b5c79d3f49e" } } ], "extra": [ 1, 80, 119, 155, 6, 132, 134, 19, 220, 102, 96, 84, 116, 5, 225, 78, 161, 150, 130, 113, 25, 122, 203, 118, 70, 37, 90, 4, 57, 40, 110, 9, 119, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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