Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0caff0a0e031328f14a65832a5ce0143b56a188b56baf7c2c808511b32e017d

Tx prefix hash: e18a390877ab2c9eaca37469fe1b45236120c2bf2df94df3b1a1c2e958901c57
Tx public key: b97295fcedcdf576b94bbb35d7864a94ba68a05b53032b33d57cd09f99abf21e
Timestamp: 1717445814 Timestamp [UCT]: 2024-06-03 20:16:54 Age [y:d:h:m:s]: 00:286:06:31:47
Block: 1036384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204590 RingCT/type: yes/0
Extra: 01b97295fcedcdf576b94bbb35d7864a94ba68a05b53032b33d57cd09f99abf21e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2eb5475abfb8e21ca8f28a4e11e7a0dabdbf48e34c3d66546c5b3f75c4989682 0.600000000000 1504911 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": 1036394, "vin": [ { "gen": { "height": 1036384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eb5475abfb8e21ca8f28a4e11e7a0dabdbf48e34c3d66546c5b3f75c4989682" } } ], "extra": [ 1, 185, 114, 149, 252, 237, 205, 245, 118, 185, 75, 187, 53, 215, 134, 74, 148, 186, 104, 160, 91, 83, 3, 43, 51, 213, 124, 208, 159, 153, 171, 242, 30, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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