Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56685a7232519fe21838446cad136967027afdd574a4aeec13d83bed7ff260eb

Tx prefix hash: b05e0bac12ec2ab1834335ff21e8cfe96fd269ce6b96ecb43aa921a7106bf253
Tx public key: b8e811e76b512579bf0bb76ef3a4f9babbebbb188a723d3c8122162b7c7c05e1
Timestamp: 1723779580 Timestamp [UCT]: 2024-08-16 03:39:40 Age [y:d:h:m:s]: 01:088:05:32:34
Block: 1088891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321519 RingCT/type: yes/0
Extra: 01b8e811e76b512579bf0bb76ef3a4f9babbebbb188a723d3c8122162b7c7c05e1021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 583c86581d5015c3647a03b1f7e15f847e5061ef65cb6fa6accf5d5d3979b1b2 0.600000000000 1563510 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": 1088901, "vin": [ { "gen": { "height": 1088891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "583c86581d5015c3647a03b1f7e15f847e5061ef65cb6fa6accf5d5d3979b1b2" } } ], "extra": [ 1, 184, 232, 17, 231, 107, 81, 37, 121, 191, 11, 183, 110, 243, 164, 249, 186, 187, 235, 187, 24, 138, 114, 61, 60, 129, 34, 22, 43, 124, 124, 5, 225, 2, 17, 0, 0, 0, 7, 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