Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61925482d7c7b3a237a8c44186be500ea56e53ea09d497b0576fac1adb6b989b

Tx prefix hash: 43c2186ef6876b50d1ebe96c8556831a1ae1c13f3afda8ba75130eda824c8b79
Tx public key: e6897e86f3ba7d9a6445724f9a6e507acf8566cd81e5ad9e13863ecd2dd085d9
Timestamp: 1728485944 Timestamp [UCT]: 2024-10-09 14:59:04 Age [y:d:h:m:s]: 00:163:06:23:28
Block: 1127907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116471 RingCT/type: yes/0
Extra: 01e6897e86f3ba7d9a6445724f9a6e507acf8566cd81e5ad9e13863ecd2dd085d902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03068e15691043c6080b4321990623ad15282bdb2e92d1c4af6bd0c8512da5b6 0.600000000000 1610720 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": 1127917, "vin": [ { "gen": { "height": 1127907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03068e15691043c6080b4321990623ad15282bdb2e92d1c4af6bd0c8512da5b6" } } ], "extra": [ 1, 230, 137, 126, 134, 243, 186, 125, 154, 100, 69, 114, 79, 154, 110, 80, 122, 207, 133, 102, 205, 129, 229, 173, 158, 19, 134, 62, 205, 45, 208, 133, 217, 2, 17, 0, 0, 0, 1, 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