Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8928d2b929a8fa35a6bfd979b85d44ffa030f6468ab0ea28adc595c951aa5948

Tx prefix hash: 482e10e5111168bcd1e63c48c5591865b302ff20ba4e72dfe338f356806c8eb1
Tx public key: bdabbd171060a503f1af5a1110b6ea9882d3541c2c152e6946a2d8aeac506afe
Timestamp: 1727190561 Timestamp [UCT]: 2024-09-24 15:09:21 Age [y:d:h:m:s]: 00:191:23:26:34
Block: 1117175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137015 RingCT/type: yes/0
Extra: 01bdabbd171060a503f1af5a1110b6ea9882d3541c2c152e6946a2d8aeac506afe02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0042db31c0436a89fd84c30217f802077781049e522ca0f8617f3b93e2510f73 0.600000000000 1597914 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": 1117185, "vin": [ { "gen": { "height": 1117175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0042db31c0436a89fd84c30217f802077781049e522ca0f8617f3b93e2510f73" } } ], "extra": [ 1, 189, 171, 189, 23, 16, 96, 165, 3, 241, 175, 90, 17, 16, 182, 234, 152, 130, 211, 84, 28, 44, 21, 46, 105, 70, 162, 216, 174, 172, 80, 106, 254, 2, 17, 0, 0, 0, 1, 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