Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e785f39d9119c40308573c003d7648cb9aba4fed70c2d3de44856634486166e7

Tx prefix hash: f412529a975962447dd267e0dd5b7769f4d873fcdac1b30b5be7be3c477c42c4
Tx public key: 0f184fb3e3812a995676d33e8b284d0199e7261229631533ce561a1bcc74eccc
Timestamp: 1701163194 Timestamp [UCT]: 2023-11-28 09:19:54 Age [y:d:h:m:s]: 01:184:18:50:21
Block: 901385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393279 RingCT/type: yes/0
Extra: 010f184fb3e3812a995676d33e8b284d0199e7261229631533ce561a1bcc74eccc02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.632903203000 dcy

stealth address amount amount idx
00: cda2f072892f64a3e00929438cba754fa2c4fcf080a3e1b3cf4195776f61f121 0.632903203000 1357944 of 0

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": 901395, "vin": [ { "gen": { "height": 901385 } } ], "vout": [ { "amount": 632903203, "target": { "key": "cda2f072892f64a3e00929438cba754fa2c4fcf080a3e1b3cf4195776f61f121" } } ], "extra": [ 1, 15, 24, 79, 179, 227, 129, 42, 153, 86, 118, 211, 62, 139, 40, 77, 1, 153, 231, 38, 18, 41, 99, 21, 51, 206, 86, 26, 27, 204, 116, 236, 204, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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