Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60065b6020e5276387b30a86ec0580aeb4370b5a1d9382e6450bdd5d381a461e

Tx prefix hash: 25563d466a848f8ba644ab1cd8c217d42e0eb5322799b8f4ad22497e6b701de5
Tx public key: be1cb6cff0bbc21ab345f0b2d056c2344c340cdeade6fdd28231c9663f76f562
Timestamp: 1744219504 Timestamp [UCT]: 2025-04-09 17:25:04 Age [y:d:h:m:s]: 00:054:04:34:18
Block: 1257845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38775 RingCT/type: yes/0
Extra: 01be1cb6cff0bbc21ab345f0b2d056c2344c340cdeade6fdd28231c9663f76f5620211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd4d31f17d2a5e1fb61f173c925b3c7d600b2b09b15d0cfa910baa1ab57fed68 0.600000000000 1744976 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": 1257855, "vin": [ { "gen": { "height": 1257845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd4d31f17d2a5e1fb61f173c925b3c7d600b2b09b15d0cfa910baa1ab57fed68" } } ], "extra": [ 1, 190, 28, 182, 207, 240, 187, 194, 26, 179, 69, 240, 178, 208, 86, 194, 52, 76, 52, 12, 222, 173, 230, 253, 210, 130, 49, 201, 102, 63, 118, 245, 98, 2, 17, 0, 0, 0, 3, 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