Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0ff9e63f5d1359cd9cdf0268839708fee7c368afc78603bd665b8fb9d9c6e6f

Tx prefix hash: e37ecbc690433981e112bbc9fac89e2c7e2603ec92b6d1a82d4117a94e1c7930
Tx public key: 4571d66c019e667ab283f3a2d752e5ae53c2497ba99ee821bb438e873b513832
Timestamp: 1712594448 Timestamp [UCT]: 2024-04-08 16:40:48 Age [y:d:h:m:s]: 01:208:19:14:09
Block: 996131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407908 RingCT/type: yes/0
Extra: 014571d66c019e667ab283f3a2d752e5ae53c2497ba99ee821bb438e873b51383202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89d81f8efff8fce0ae1a243a47c87dc0f39c48e52921425bb2fcd9a849004759 0.600000000000 1456547 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": 996141, "vin": [ { "gen": { "height": 996131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89d81f8efff8fce0ae1a243a47c87dc0f39c48e52921425bb2fcd9a849004759" } } ], "extra": [ 1, 69, 113, 214, 108, 1, 158, 102, 122, 178, 131, 243, 162, 215, 82, 229, 174, 83, 194, 73, 123, 169, 158, 232, 33, 187, 67, 142, 135, 59, 81, 56, 50, 2, 17, 0, 0, 0, 6, 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