Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5be34b534cc62d32cc8a4a8922c5a5f307e485fe6d943edf985d1979ca816c69

Tx prefix hash: d24f6ef96aea9684477573a7c43f93c6b5f6d619c3ddd2295d364bd4c3ef7430
Tx public key: de048a79962a6c7315880e9cfa4baac3d7c97afdb161307745d03b60ef2dd1c6
Timestamp: 1760561299 Timestamp [UCT]: 2025-10-15 20:48:19 Age [y:d:h:m:s]: 00:081:23:28:46
Block: 1390709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58717 RingCT/type: yes/0
Extra: 01de048a79962a6c7315880e9cfa4baac3d7c97afdb161307745d03b60ef2dd1c602110000000a2609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c1b71a06592644ba5764753f5bbd31a23979024aad15ed393a8efede1d3800c 0.600000000000 1878956 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": 1390719, "vin": [ { "gen": { "height": 1390709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c1b71a06592644ba5764753f5bbd31a23979024aad15ed393a8efede1d3800c" } } ], "extra": [ 1, 222, 4, 138, 121, 150, 42, 108, 115, 21, 136, 14, 156, 250, 75, 170, 195, 215, 201, 122, 253, 177, 97, 48, 119, 69, 208, 59, 96, 239, 45, 209, 198, 2, 17, 0, 0, 0, 10, 38, 9, 179, 160, 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