Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646f92c526907c778d6dbb90019ff7d96a0e00140c422526f48c865a50eaceec

Tx prefix hash: b6a6fa5ea2c6b354dc06343cbc25e42d646e0bfb3729aa3f2201b22756cd0d97
Tx public key: 602c871a119b0da11d8fa1b54c639a6c7020dd00347c52aea10cb366c4ae2ee6
Timestamp: 1694517575 Timestamp [UCT]: 2023-09-12 11:19:35 Age [y:d:h:m:s]: 01:166:02:47:14
Block: 846476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379786 RingCT/type: yes/0
Extra: 01602c871a119b0da11d8fa1b54c639a6c7020dd00347c52aea10cb366c4ae2ee60211000000034fd716a6000000000000000000

1 output(s) for total of 0.962258461000 dcy

stealth address amount amount idx
00: 1a7e568ce5fd95c36b83bf3b23c24765af79486dc5cefbf3d643d1ee0203af6d 0.962258461000 1299940 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": 846486, "vin": [ { "gen": { "height": 846476 } } ], "vout": [ { "amount": 962258461, "target": { "key": "1a7e568ce5fd95c36b83bf3b23c24765af79486dc5cefbf3d643d1ee0203af6d" } } ], "extra": [ 1, 96, 44, 135, 26, 17, 155, 13, 161, 29, 143, 161, 181, 76, 99, 154, 108, 112, 32, 221, 0, 52, 124, 82, 174, 161, 12, 179, 102, 196, 174, 46, 230, 2, 17, 0, 0, 0, 3, 79, 215, 22, 166, 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