Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ae655834302b98e57cc37e329ad76382c3f8efe05e3d13ffc978eaa0e3944fe

Tx prefix hash: 6c60178f13807029ab4a7192094ef66d510e23a4d2887515108c11f0aaf5fd10
Tx public key: fec57bc802e0fad226da1cc7bd5f59b6aa2e35d23437f7be6fd44c218357cbab
Timestamp: 1736693953 Timestamp [UCT]: 2025-01-12 14:59:13 Age [y:d:h:m:s]: 00:156:04:35:17
Block: 1195816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111335 RingCT/type: yes/0
Extra: 01fec57bc802e0fad226da1cc7bd5f59b6aa2e35d23437f7be6fd44c218357cbab0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea36cbc12057c54285977a4fe39b6e5768e230363acf8a71a824f63ed3372d0d 0.600000000000 1682409 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": 1195826, "vin": [ { "gen": { "height": 1195816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea36cbc12057c54285977a4fe39b6e5768e230363acf8a71a824f63ed3372d0d" } } ], "extra": [ 1, 254, 197, 123, 200, 2, 224, 250, 210, 38, 218, 28, 199, 189, 95, 89, 182, 170, 46, 53, 210, 52, 55, 247, 190, 111, 212, 76, 33, 131, 87, 203, 171, 2, 17, 0, 0, 0, 8, 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