Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef087ba12cb48ed953f2cb648e413b971c22edc29de902db1c1b9064510e9107

Tx prefix hash: c9a6511a52e49db0342c970fae704a6081b2f8e51d23eb9da54e1bcc4c81589e
Tx public key: 1d3203a31886795c1ce326a373c85ff1d0a963352bf1e1977f3646f9c32fbda8
Timestamp: 1721383359 Timestamp [UCT]: 2024-07-19 10:02:39 Age [y:d:h:m:s]: 00:219:21:00:46
Block: 1069037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157017 RingCT/type: yes/0
Extra: 011d3203a31886795c1ce326a373c85ff1d0a963352bf1e1977f3646f9c32fbda802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 501309fdd6b55dbeccedfe9cedea6f0d5b8e06fa860a753cc38c16720a101cf0 0.600000000000 1540304 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": 1069047, "vin": [ { "gen": { "height": 1069037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "501309fdd6b55dbeccedfe9cedea6f0d5b8e06fa860a753cc38c16720a101cf0" } } ], "extra": [ 1, 29, 50, 3, 163, 24, 134, 121, 92, 28, 227, 38, 163, 115, 200, 95, 241, 208, 169, 99, 53, 43, 241, 225, 151, 127, 54, 70, 249, 195, 47, 189, 168, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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