Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e0e24b797b7f633c1580b39f7e1c9bcba64843804d53cfe4da87e61468f6649

Tx prefix hash: b842f180a7c85b1ae2d77a1fc2cba890acee829ed3530c0c1660aca03c35f203
Tx public key: ee4cfa048d8aa62e2ab2281a6ab405e65cc89aeef0d48e9fc163299d300ac273
Timestamp: 1735459685 Timestamp [UCT]: 2024-12-29 08:08:05 Age [y:d:h:m:s]: 00:324:21:51:45
Block: 1185589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229740 RingCT/type: yes/0
Extra: 01ee4cfa048d8aa62e2ab2281a6ab405e65cc89aeef0d48e9fc163299d300ac2730211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b64d59270084b006e2507a3abb2e19654c2b5411d4594c56f4166bb3fc655dbb 0.600000000000 1672064 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": 1185599, "vin": [ { "gen": { "height": 1185589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b64d59270084b006e2507a3abb2e19654c2b5411d4594c56f4166bb3fc655dbb" } } ], "extra": [ 1, 238, 76, 250, 4, 141, 138, 166, 46, 42, 178, 40, 26, 106, 180, 5, 230, 92, 200, 154, 238, 240, 212, 142, 159, 193, 99, 41, 157, 48, 10, 194, 115, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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