Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 775bae57d4f58eab6a9282df32427d8c4f08bff208a135e2adbcbbf83c3e4dac

Tx prefix hash: eb891aa81b1757f453b4236569fc3aaebf1a1fad841f6017c1ff4e01f7268aa3
Tx public key: c0c610b4ce40e94ded962534007651d810e7ca9cc9473d5b827f77ea098a729b
Timestamp: 1703453296 Timestamp [UCT]: 2023-12-24 21:28:16 Age [y:d:h:m:s]: 01:100:12:24:04
Block: 920372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332958 RingCT/type: yes/0
Extra: 01c0c610b4ce40e94ded962534007651d810e7ca9cc9473d5b827f77ea098a729b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1d9bae0ff8b3d37e9843c2b77ffa71a6da705d57ca5b474bbcc1f36ef303306 0.600000000000 1378050 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": 920382, "vin": [ { "gen": { "height": 920372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1d9bae0ff8b3d37e9843c2b77ffa71a6da705d57ca5b474bbcc1f36ef303306" } } ], "extra": [ 1, 192, 198, 16, 180, 206, 64, 233, 77, 237, 150, 37, 52, 0, 118, 81, 216, 16, 231, 202, 156, 201, 71, 61, 91, 130, 127, 119, 234, 9, 138, 114, 155, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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