Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f256df5815ed3825e2972ca9e4677471df09d328c832ff08dd98f4300c2a65e

Tx prefix hash: 158347d8fd3c890db59d7ff5b9d7bacd5884f9b8694ee008723347b3f8c8c95e
Tx public key: 9adeca7dbc8f640d41b9bc172bf4bfc7b4d6d0e5b13eb22e2df53141d4341741
Timestamp: 1735992709 Timestamp [UCT]: 2025-01-04 12:11:49 Age [y:d:h:m:s]: 00:169:19:52:26
Block: 1190011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120995 RingCT/type: yes/0
Extra: 019adeca7dbc8f640d41b9bc172bf4bfc7b4d6d0e5b13eb22e2df53141d434174102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b2ba3c6ff4d3da8078fef137ab20e3f624c7d9d5045695ba70df61781acdc2e 0.600000000000 1676526 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": 1190021, "vin": [ { "gen": { "height": 1190011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b2ba3c6ff4d3da8078fef137ab20e3f624c7d9d5045695ba70df61781acdc2e" } } ], "extra": [ 1, 154, 222, 202, 125, 188, 143, 100, 13, 65, 185, 188, 23, 43, 244, 191, 199, 180, 214, 208, 229, 177, 62, 178, 46, 45, 245, 49, 65, 212, 52, 23, 65, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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