Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f0239162e5f7454530abf6574658de638e5fe469b83711470d7cb6ea6b989c5

Tx prefix hash: 986ef21a09f809b513e33bbfe40f3adb950bf94683003fd39a2c1cb9e1edcacf
Tx public key: b488fa2471454f74c4b18602f5a57e7411a42ff9c18c81f34a95f4b01a26b7bb
Timestamp: 1697403668 Timestamp [UCT]: 2023-10-15 21:01:08 Age [y:d:h:m:s]: 01:185:17:51:12
Block: 870428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393787 RingCT/type: yes/0
Extra: 01b488fa2471454f74c4b18602f5a57e7411a42ff9c18c81f34a95f4b01a26b7bb02110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.801513296000 dcy

stealth address amount amount idx
00: 170915f74092833adeab39cacb793a96384dd885bed9ab602deae398cdb75723 0.801513296000 1325307 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": 870438, "vin": [ { "gen": { "height": 870428 } } ], "vout": [ { "amount": 801513296, "target": { "key": "170915f74092833adeab39cacb793a96384dd885bed9ab602deae398cdb75723" } } ], "extra": [ 1, 180, 136, 250, 36, 113, 69, 79, 116, 196, 177, 134, 2, 245, 165, 126, 116, 17, 164, 47, 249, 193, 140, 129, 243, 74, 149, 244, 176, 26, 38, 183, 187, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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