Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7330e07cfcecd3f70c2e294c5112005cdf6ac1cc347e72e5a126c2c042c9bf86

Tx prefix hash: 6780bac7815714ecf073924fe872e17ce870bb0257538866afcd4c8ae292f62b
Tx public key: f5498b8ead47eb9d15bde1c79d4beae465e0412bdbb6b4d113e1f8fcd140b399
Timestamp: 1725218889 Timestamp [UCT]: 2024-09-01 19:28:09 Age [y:d:h:m:s]: 00:212:14:30:46
Block: 1100829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151788 RingCT/type: yes/0
Extra: 01f5498b8ead47eb9d15bde1c79d4beae465e0412bdbb6b4d113e1f8fcd140b399021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23f9ca3b21a10d59ef7bc585c6896537bce5be823045b6e75497a6b6b5fe7e56 0.600000000000 1576810 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": 1100839, "vin": [ { "gen": { "height": 1100829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23f9ca3b21a10d59ef7bc585c6896537bce5be823045b6e75497a6b6b5fe7e56" } } ], "extra": [ 1, 245, 73, 139, 142, 173, 71, 235, 157, 21, 189, 225, 199, 157, 75, 234, 228, 101, 224, 65, 43, 219, 182, 180, 209, 19, 225, 248, 252, 209, 64, 179, 153, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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