Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb557c82e9b6d34738c7fac87c2ba82f6b0ca7d88d430b059e4074c9a37c96db

Tx prefix hash: c0fea08240fdaa908fd33bb8f6f46a362efd4e4bae60a8896b27fb89a16e3b82
Tx public key: 34463a648712f21974acc056573001039ac783344596f929bd6a3b4ec93f046a
Timestamp: 1747520534 Timestamp [UCT]: 2025-05-17 22:22:14 Age [y:d:h:m:s]: 00:192:16:48:14
Block: 1285175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135441 RingCT/type: yes/0
Extra: 0134463a648712f21974acc056573001039ac783344596f929bd6a3b4ec93f046a0211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29e9c83a3b23b39ec9b972fae8b975e4ea833c842b0e1617f88ae46c3b300efe 0.600000000000 1772638 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": 1285185, "vin": [ { "gen": { "height": 1285175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29e9c83a3b23b39ec9b972fae8b975e4ea833c842b0e1617f88ae46c3b300efe" } } ], "extra": [ 1, 52, 70, 58, 100, 135, 18, 242, 25, 116, 172, 192, 86, 87, 48, 1, 3, 154, 199, 131, 52, 69, 150, 249, 41, 189, 106, 59, 78, 201, 63, 4, 106, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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