Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ae8e647fc5bddf6e2826f91d376c2f6c65075666c8f0d54d9a2190b517335e

Tx prefix hash: 514e87867fb6155a92ef4d0fd250a92b103057ab7c5e712b5730d86ce001d324
Tx public key: ed38eed90d8b77a6a7f2e090fdcd394d04f9f4470d834e8bf358e1674de60045
Timestamp: 1726089868 Timestamp [UCT]: 2024-09-11 21:24:28 Age [y:d:h:m:s]: 00:216:05:10:11
Block: 1108036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154380 RingCT/type: yes/0
Extra: 01ed38eed90d8b77a6a7f2e090fdcd394d04f9f4470d834e8bf358e1674de60045021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2374ccb127a117e9a9be43f35a5ec3a2ed0fb6a50152e390b75e4805ab76d7b 0.600000000000 1585793 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": 1108046, "vin": [ { "gen": { "height": 1108036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2374ccb127a117e9a9be43f35a5ec3a2ed0fb6a50152e390b75e4805ab76d7b" } } ], "extra": [ 1, 237, 56, 238, 217, 13, 139, 119, 166, 167, 242, 224, 144, 253, 205, 57, 77, 4, 249, 244, 71, 13, 131, 78, 139, 243, 88, 225, 103, 77, 230, 0, 69, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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