Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1759b82e1871dc2982ad99cbc52672f01e28b0f8ee618894d2b7d25c5f188a9

Tx prefix hash: 07bf505de623e3b77529c7c195f33c996647c0adf5b83b2fe7ed34526f64ef7e
Tx public key: b8a5e0facb7a5021523db969fb62e4104e3524ec7904af1d124c5c467e1c89f6
Timestamp: 1754492862 Timestamp [UCT]: 2025-08-06 15:07:42 Age [y:d:h:m:s]: 00:139:08:58:47
Block: 1341533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98667 RingCT/type: yes/0
Extra: 01b8a5e0facb7a5021523db969fb62e4104e3524ec7904af1d124c5c467e1c89f6021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e58198c60945445220bde2e0ede5dcf989587c1a80f79c0453cb1e200ed0c76 0.600000000000 1829358 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": 1341543, "vin": [ { "gen": { "height": 1341533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e58198c60945445220bde2e0ede5dcf989587c1a80f79c0453cb1e200ed0c76" } } ], "extra": [ 1, 184, 165, 224, 250, 203, 122, 80, 33, 82, 61, 185, 105, 251, 98, 228, 16, 78, 53, 36, 236, 121, 4, 175, 29, 18, 76, 92, 70, 126, 28, 137, 246, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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