Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb2e7ee00c9f3ced787738ecafe9cbda3f9efa8f4523bf200bc548af4500ff74

Tx prefix hash: 1796dcc49aa6b6c3796557b1e58055e15d4b214f6ece0e0450f66465b7178d7a
Tx public key: bd1cd425d9b53c4a78dcf611e24311f7b5eb7059543ea44be7a2b5e3ebaf289d
Timestamp: 1755118884 Timestamp [UCT]: 2025-08-13 21:01:24 Age [y:d:h:m:s]: 00:163:14:44:35
Block: 1346285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116292 RingCT/type: yes/0
Extra: 01bd1cd425d9b53c4a78dcf611e24311f7b5eb7059543ea44be7a2b5e3ebaf289d02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 683623ed4bc8d4355ad55e555f1c87d0d8a6026d34cbe74f56a12cc16fa442c5 0.600000000000 1834184 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": 1346295, "vin": [ { "gen": { "height": 1346285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "683623ed4bc8d4355ad55e555f1c87d0d8a6026d34cbe74f56a12cc16fa442c5" } } ], "extra": [ 1, 189, 28, 212, 37, 217, 181, 60, 74, 120, 220, 246, 17, 226, 67, 17, 247, 181, 235, 112, 89, 84, 62, 164, 75, 231, 162, 181, 227, 235, 175, 40, 157, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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