Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc75ef85e0df617edc722ab566cd983ba99b17aa3d1c249a2597c040386b7087

Tx prefix hash: ad7eaa61239f9b2ae803c5d5d50e5253d8aedb74dfeea06ce0859b879630e7ea
Tx public key: dacd0c6104f8b191659e222a5ff6c27f5ab9c866ed569913bbad519f4d8fa131
Timestamp: 1705776139 Timestamp [UCT]: 2024-01-20 18:42:19 Age [y:d:h:m:s]: 01:130:09:23:40
Block: 939605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354337 RingCT/type: yes/0
Extra: 01dacd0c6104f8b191659e222a5ff6c27f5ab9c866ed569913bbad519f4d8fa1310211000000100011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6556e715012e4a9c19d1d8781476b029bdd1588fd1609a15ab8a9e6432982207 0.600000000000 1397713 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": 939615, "vin": [ { "gen": { "height": 939605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6556e715012e4a9c19d1d8781476b029bdd1588fd1609a15ab8a9e6432982207" } } ], "extra": [ 1, 218, 205, 12, 97, 4, 248, 177, 145, 101, 158, 34, 42, 95, 246, 194, 127, 90, 185, 200, 102, 237, 86, 153, 19, 187, 173, 81, 159, 77, 143, 161, 49, 2, 17, 0, 0, 0, 16, 0, 17, 5, 91, 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