Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23d8d114bebcf60e16a9f706fe30647f71ee1b211c5d8706855ae8682b68bf6e

Tx prefix hash: e9992e058f81364f5664ae4c871350bd44cdfe59b8ab65b3a13cd093b7bab690
Tx public key: 10753127595e7b767fdeff567a72c16a3b32d70473f0213a8f2fbfe99e54115b
Timestamp: 1711159267 Timestamp [UCT]: 2024-03-23 02:01:07 Age [y:d:h:m:s]: 01:003:10:35:27
Block: 984281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263397 RingCT/type: yes/0
Extra: 0110753127595e7b767fdeff567a72c16a3b32d70473f0213a8f2fbfe99e54115b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1b11a670759bc1805b9886c31d831b94503b49f699efe6b80e582a848a77398 0.600000000000 1444450 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": 984291, "vin": [ { "gen": { "height": 984281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1b11a670759bc1805b9886c31d831b94503b49f699efe6b80e582a848a77398" } } ], "extra": [ 1, 16, 117, 49, 39, 89, 94, 123, 118, 127, 222, 255, 86, 122, 114, 193, 106, 59, 50, 215, 4, 115, 240, 33, 58, 143, 47, 191, 233, 158, 84, 17, 91, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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