Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e5c269de5b5d1670d7f7385666d00fe97b5dcdef2788d25ae4efa53c434047f

Tx prefix hash: ee6eafeddcae1a9840b67fc3a844504d882aa29f967afee753dcc69a7cfed40e
Tx public key: a8ab5845a961053101b5a4bcefe8bd3c87c8b2da8cdc761cb16142cc85324091
Timestamp: 1738301645 Timestamp [UCT]: 2025-01-31 05:34:05 Age [y:d:h:m:s]: 00:136:17:14:21
Block: 1208873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97671 RingCT/type: yes/0
Extra: 01a8ab5845a961053101b5a4bcefe8bd3c87c8b2da8cdc761cb16142cc853240910211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48b9d69044977d5ce79dd959117d9f323fca7f1993f88b407dca754422dcc4ae 0.600000000000 1695608 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": 1208883, "vin": [ { "gen": { "height": 1208873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48b9d69044977d5ce79dd959117d9f323fca7f1993f88b407dca754422dcc4ae" } } ], "extra": [ 1, 168, 171, 88, 69, 169, 97, 5, 49, 1, 181, 164, 188, 239, 232, 189, 60, 135, 200, 178, 218, 140, 220, 118, 28, 177, 97, 66, 204, 133, 50, 64, 145, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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