Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5e378ec51b29c2c0802be98ceaa8814a7f85734edf544a9e5da88ec3cfc9c64

Tx prefix hash: 0779c40cdecce7fd7aa7982f6fe6f282fd19100b4a06bcda5120ac97f9c6c7d8
Tx public key: 103e420a855678709b7431108a6fa2caba6f0bdf72c610df70d81cb0c96ddda4
Timestamp: 1722099874 Timestamp [UCT]: 2024-07-27 17:04:34 Age [y:d:h:m:s]: 00:186:12:16:16
Block: 1074964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133171 RingCT/type: yes/0
Extra: 01103e420a855678709b7431108a6fa2caba6f0bdf72c610df70d81cb0c96ddda402110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b3ed4983a2e95b42aef8e290f382f42165c1510b839e31908ea529be4a3f05e 0.600000000000 1547483 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": 1074974, "vin": [ { "gen": { "height": 1074964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b3ed4983a2e95b42aef8e290f382f42165c1510b839e31908ea529be4a3f05e" } } ], "extra": [ 1, 16, 62, 66, 10, 133, 86, 120, 112, 155, 116, 49, 16, 138, 111, 162, 202, 186, 111, 11, 223, 114, 198, 16, 223, 112, 216, 28, 176, 201, 109, 221, 164, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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