Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61b16dfc898f0c48c492904a413c2d43c1679ab14b9e6250bba23c3d5f3a7b3a

Tx prefix hash: d17ae48b51122b7f01eec347cf982e258259c5609380ebdf7f29769466b3c0c0
Tx public key: ca1b792a24281a1dffb0629b8dfa2539c2ee6bb96aa3e7f059654745aadecab0
Timestamp: 1745774181 Timestamp [UCT]: 2025-04-27 17:16:21 Age [y:d:h:m:s]: 00:015:17:36:05
Block: 1270724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11250 RingCT/type: yes/0
Extra: 01ca1b792a24281a1dffb0629b8dfa2539c2ee6bb96aa3e7f059654745aadecab00211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5061fe8f5264340a5d8f442fd85e3253084e748611b26b8e4885fcaecbc8bee1 0.600000000000 1757969 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": 1270734, "vin": [ { "gen": { "height": 1270724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5061fe8f5264340a5d8f442fd85e3253084e748611b26b8e4885fcaecbc8bee1" } } ], "extra": [ 1, 202, 27, 121, 42, 36, 40, 26, 29, 255, 176, 98, 155, 141, 250, 37, 57, 194, 238, 107, 185, 106, 163, 231, 240, 89, 101, 71, 69, 170, 222, 202, 176, 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