Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44966970faea72d1fec4a2f147d84bc13f61a86d7d2a83e84bc0ae5eaa2efd4f

Tx prefix hash: d4f9f467775c6e077302082edbedc17734b5948f85b0a77c09460be5b6a687b2
Tx public key: 315a25a512f5d6ab2987069087195004e184c0b68b6c8ccf41ac00decea4b6d0
Timestamp: 1760747265 Timestamp [UCT]: 2025-10-18 00:27:45 Age [y:d:h:m:s]: 00:068:19:54:30
Block: 1392265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49267 RingCT/type: yes/0
Extra: 01315a25a512f5d6ab2987069087195004e184c0b68b6c8ccf41ac00decea4b6d00211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3ee5993e7026294d1d3d4a573a9419c0c2ce92178db4361cfe570fc9c52836 0.600000000000 1880516 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": 1392275, "vin": [ { "gen": { "height": 1392265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3ee5993e7026294d1d3d4a573a9419c0c2ce92178db4361cfe570fc9c52836" } } ], "extra": [ 1, 49, 90, 37, 165, 18, 245, 214, 171, 41, 135, 6, 144, 135, 25, 80, 4, 225, 132, 192, 182, 139, 108, 140, 207, 65, 172, 0, 222, 206, 164, 182, 208, 2, 17, 0, 0, 0, 2, 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