Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25a6776810e010f4794742b81db53e399f76faa0d9499476f1650c38e5fe86c7

Tx prefix hash: a8801be0e761f7a3a9794ba2b994a73eb5d154631a09ab026cb60870468293a3
Tx public key: 8c3f60ac2f5098b7b8779e0f174b3c9ebd9420f202a83dd95ff63dd905ccfb37
Timestamp: 1723202083 Timestamp [UCT]: 2024-08-09 11:14:43 Age [y:d:h:m:s]: 00:235:14:17:11
Block: 1084100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168253 RingCT/type: yes/0
Extra: 018c3f60ac2f5098b7b8779e0f174b3c9ebd9420f202a83dd95ff63dd905ccfb3702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95c65a58fb556fd7417600d619e0b8da4390372000115778ca9055e9f8f9a017 0.600000000000 1558255 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": 1084110, "vin": [ { "gen": { "height": 1084100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95c65a58fb556fd7417600d619e0b8da4390372000115778ca9055e9f8f9a017" } } ], "extra": [ 1, 140, 63, 96, 172, 47, 80, 152, 183, 184, 119, 158, 15, 23, 75, 60, 158, 189, 148, 32, 242, 2, 168, 61, 217, 95, 246, 61, 217, 5, 204, 251, 55, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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