Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18077396a4e2b867cd36fbfee4b859d3a484aae2c4e9715c25861bb6fa293b18

Tx prefix hash: e295b63e97240334056723b2ac614962c7df1151e4e56ff2ab3c484a6466ead7
Tx public key: f639e97254ed978ae7a83bda4c4bb2648598759551a0c77b475a5b15ab97692d
Timestamp: 1713186289 Timestamp [UCT]: 2024-04-15 13:04:49 Age [y:d:h:m:s]: 01:040:05:50:42
Block: 1001063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289742 RingCT/type: yes/0
Extra: 01f639e97254ed978ae7a83bda4c4bb2648598759551a0c77b475a5b15ab97692d0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7525675ac01bfadcc627f588d486289ff373fd585d159b3aa4eb752e12142d5b 0.600000000000 1461565 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": 1001073, "vin": [ { "gen": { "height": 1001063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7525675ac01bfadcc627f588d486289ff373fd585d159b3aa4eb752e12142d5b" } } ], "extra": [ 1, 246, 57, 233, 114, 84, 237, 151, 138, 231, 168, 59, 218, 76, 75, 178, 100, 133, 152, 117, 149, 81, 160, 199, 123, 71, 90, 91, 21, 171, 151, 105, 45, 2, 17, 0, 0, 0, 7, 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