Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e3e1c6e0ad34f8dca97d1a40fac485b86063ba83744056e57eb7385410a2129

Tx prefix hash: b751ed52a8658433c6b11e552724030a861eedb3df13904910ab4470af4e489e
Tx public key: 28c247b13acafa5a18ac679a82f0b71e475f9b0af0a76c0f6fac4ca1039c0356
Timestamp: 1727841215 Timestamp [UCT]: 2024-10-02 03:53:35 Age [y:d:h:m:s]: 00:112:22:43:15
Block: 1122564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80704 RingCT/type: yes/0
Extra: 0128c247b13acafa5a18ac679a82f0b71e475f9b0af0a76c0f6fac4ca1039c035602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ede096c344f0f4ccd0f6a753b0a5ef0fffc847a1edc032d9e06cbf2a10077291 0.600000000000 1605033 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": 1122574, "vin": [ { "gen": { "height": 1122564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ede096c344f0f4ccd0f6a753b0a5ef0fffc847a1edc032d9e06cbf2a10077291" } } ], "extra": [ 1, 40, 194, 71, 177, 58, 202, 250, 90, 24, 172, 103, 154, 130, 240, 183, 30, 71, 95, 155, 10, 240, 167, 108, 15, 111, 172, 76, 161, 3, 156, 3, 86, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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