Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e99f989891de0743177b5b4df5c127b37ce26fdf49db8667b6412c32b4026cb4

Tx prefix hash: 299f2ebf826ab02d4347a898c6e8172ccd6608ce7a97387d438be61ece4d4fdd
Tx public key: 8a4251589ca90c4fb53b806e8f9d16638b01b0da9ac3045be32f2a4b42e2448e
Timestamp: 1723069605 Timestamp [UCT]: 2024-08-07 22:26:45 Age [y:d:h:m:s]: 00:275:13:27:04
Block: 1083006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196847 RingCT/type: yes/0
Extra: 018a4251589ca90c4fb53b806e8f9d16638b01b0da9ac3045be32f2a4b42e2448e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef0844c393187a2a5ba70dfa94a3abab169e6f54c7b8da32f278d4370946d1b6 0.600000000000 1556841 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": 1083016, "vin": [ { "gen": { "height": 1083006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef0844c393187a2a5ba70dfa94a3abab169e6f54c7b8da32f278d4370946d1b6" } } ], "extra": [ 1, 138, 66, 81, 88, 156, 169, 12, 79, 181, 59, 128, 110, 143, 157, 22, 99, 139, 1, 176, 218, 154, 195, 4, 91, 227, 47, 42, 75, 66, 226, 68, 142, 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