Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69deefc769c7f6347d004832fea743ad88904c2038715ea0f1e1ef486d09e989

Tx prefix hash: 7a586962015d67da85caa7e242afd0501d54bef92758c766ddc6933aba1ad9e8
Tx public key: 3fc3be92173edae0e92c9a869427e251c1425d1fe1f2a7115ea06d53d70ae226
Timestamp: 1739148884 Timestamp [UCT]: 2025-02-10 00:54:44 Age [y:d:h:m:s]: 00:317:01:01:22
Block: 1215870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224389 RingCT/type: yes/0
Extra: 013fc3be92173edae0e92c9a869427e251c1425d1fe1f2a7115ea06d53d70ae22602110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0227b1e9f481e8f3ebea5e775e2ae36292836671fc3c699e02440e266eafca4f 0.600000000000 1702669 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": 1215880, "vin": [ { "gen": { "height": 1215870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0227b1e9f481e8f3ebea5e775e2ae36292836671fc3c699e02440e266eafca4f" } } ], "extra": [ 1, 63, 195, 190, 146, 23, 62, 218, 224, 233, 44, 154, 134, 148, 39, 226, 81, 193, 66, 93, 31, 225, 242, 167, 17, 94, 160, 109, 83, 215, 10, 226, 38, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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