Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11935d3d5ee91e726750fb0fcdb7eec0636fbe632b730f70b7b45df987bb2b10

Tx prefix hash: d8adb8824bbaabb6d39fdaf233e0507a5be33163d01ca686f55bd6bbe2c95dbf
Tx public key: a0c630ea4f0a840397e028cb9986b57f85f066bbd25d153b574e36ccab9c7cc5
Timestamp: 1683653269 Timestamp [UCT]: 2023-05-09 17:27:49 Age [y:d:h:m:s]: 02:153:01:40:37
Block: 756487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 629159 RingCT/type: yes/0
Extra: 01a0c630ea4f0a840397e028cb9986b57f85f066bbd25d153b574e36ccab9c7cc5021100000003b3164c24000000000000000000

1 output(s) for total of 1.911810005000 dcy

stealth address amount amount idx
00: 3d76ca371f53e6e49b12f58978b31f4a4bdf614195f22033cdab21594d827221 1.911810005000 1204866 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": 756497, "vin": [ { "gen": { "height": 756487 } } ], "vout": [ { "amount": 1911810005, "target": { "key": "3d76ca371f53e6e49b12f58978b31f4a4bdf614195f22033cdab21594d827221" } } ], "extra": [ 1, 160, 198, 48, 234, 79, 10, 132, 3, 151, 224, 40, 203, 153, 134, 181, 127, 133, 240, 102, 187, 210, 93, 21, 59, 87, 78, 54, 204, 171, 156, 124, 197, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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