Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b524a56002ee0608e2697d2c194a9cb6597afbd51a40e1332f139dcfb82269e

Tx prefix hash: cb2b2837c91e0858f886a6a677bfc5bcc5db27f474ab23ce51f8cb0a2bf2ce81
Tx public key: c7ad5d44430d159c64774ae94105b14acf99371d184a441b982878a41c65aa22
Timestamp: 1711194540 Timestamp [UCT]: 2024-03-23 11:49:00 Age [y:d:h:m:s]: 01:086:08:07:46
Block: 984583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322579 RingCT/type: yes/0
Extra: 01c7ad5d44430d159c64774ae94105b14acf99371d184a441b982878a41c65aa2202110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f81741e5fd9b3255826803b6966de64d477e0ca418e6ae7c3679d0c677e7a7bc 0.600000000000 1444754 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": 984593, "vin": [ { "gen": { "height": 984583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f81741e5fd9b3255826803b6966de64d477e0ca418e6ae7c3679d0c677e7a7bc" } } ], "extra": [ 1, 199, 173, 93, 68, 67, 13, 21, 156, 100, 119, 74, 233, 65, 5, 177, 74, 207, 153, 55, 29, 24, 74, 68, 27, 152, 40, 120, 164, 28, 101, 170, 34, 2, 17, 0, 0, 0, 10, 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