Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d36addf5d680449f9d5270d5f1b7ae784ae64c77064faafe12f5c3f3b655f45

Tx prefix hash: 2cc69c9e95422e2500588f83529e3c93d831dd8bc2bc1c407b25ab95c04efeba
Tx public key: 3adf19ca6fbb4d48082a8d10b4c9425cbd1e88cd18779cc7cc9b897440987b14
Timestamp: 1712851675 Timestamp [UCT]: 2024-04-11 16:07:55 Age [y:d:h:m:s]: 01:035:21:39:22
Block: 998268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286657 RingCT/type: yes/0
Extra: 013adf19ca6fbb4d48082a8d10b4c9425cbd1e88cd18779cc7cc9b897440987b1402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f35ff3ed5ffe67ad77b0987c475fe32ca559b9bd3debe0c975d0f980d4a9783 0.600000000000 1458714 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": 998278, "vin": [ { "gen": { "height": 998268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f35ff3ed5ffe67ad77b0987c475fe32ca559b9bd3debe0c975d0f980d4a9783" } } ], "extra": [ 1, 58, 223, 25, 202, 111, 187, 77, 72, 8, 42, 141, 16, 180, 201, 66, 92, 189, 30, 136, 205, 24, 119, 156, 199, 204, 155, 137, 116, 64, 152, 123, 20, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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